-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify headers and response code for external content #351
Conversation
index.html
Outdated
<pre> | ||
Link: <http://www.w3.org/ns/ldp#Resource>;rel="type" | ||
Link: <http://www.w3.org/ns/ldp#NonRDFSource>;rel="type" | ||
Link: <http://host/fcrepo/image/fcr:metadata>; rel="describedby" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we show these as separate Link
headers or combine into one with commas? I think if we show separately we should add a note that they might be combined (per https://tools.ietf.org/html/rfc8288#section-3)
index.html
Outdated
@@ -671,6 +681,10 @@ <h4>Redirected and Proxied External Content</h4> | |||
<code>GET</code> and <code>HEAD</code> requests to any external <a>LDP-NR</a> MUST correctly | |||
respond to the <code>Want-Digest</code> header defined in [[!RFC3230]]. | |||
</p> | |||
<p id='external-content-redirect-status'> | |||
A successful response to external content with <code>handling</code> of <code>redirect</code> MUST have |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
response to a GET
and HEAD
request for external content?
* Clarify headers and response code for external content Resolves: fcrepo#345 * Address code review comments
Resolves: #345